**********************Windows NT Server Upgrade**********************

Thank you for purchasing the Microsoft(R) Windows NT(TM) Server 3.51 Upgrade
for Microsoft LAN Manager for OS/2(R). This document includes information that was 
not available in time to include in the Upgrade Guide. 


***Read this file and the Upgrade Guide manual completely before attempting to install 
or use the Upgrade. They contain important information on the steps to take before 
performing the Upgrade.


Contents
================
1.0  About the Microsoft Windows NT Server 3.51 Upgrade
   1.1  Upgrading Novell NetWare Servers
2.0  Installing the Upgrade Utilities
3.0  Upgrade Notes, Corrections, and Clarifications
   3.1  Upgrade Guide is Available Online
   3.2  Services for Macintosh
   3.3  USERCONV Command Line Options
   3.4  USERCONV Exit Option
   3.5  RESTENV Can't Reestablish a Network Share
   3.6  Net Logon Service Parameters
   3.7  ACLCOMP.EXE
   3.8  PORTUAS: Preventing Interruptions from a BDC Synchronization

================
1.0  About the Microsoft Windows NT Server 3.51 Upgrade

The Upgrade software utilities convert LAN Manager for OS/2 server information for use in a Windows NT Server computer. The Upgrade utilities operate only on LAN Manager versions 2.1a and higher.   
They cannot upgrade any other network operating system besides LAN Manager, including PC LAN Server, Banyan(R) VINES(R), and Novell(R) NetWare(R).

This is a Windows NT Server maintenance release. Although the upgrade software loaded 
on your machine is 3.51, some version numbers in the documentation and software do not 
reflect the upgrade.

-----------------------
1.1 Upgrading Novell NetWare Servers

The Microsoft Windows NT Server 3.51 Upgrade does not convert Novell NetWare servers. 
However, you can transfer information from a Novell NetWare server to a computer 
running Windows NT Server using the Migration Tool for NetWare. For more information, 
see the Services for NetWare Networks manual included in the Windows NT Server 
package.

================
2.0  Installing the Upgrade Utilities

Before installing the Upgrade Utilities, read Chapter 3, "Preparing to Upgrade," in the 
Windows NT Server Upgrade Guide, as well as the rest of this file.

The Windows NT Server CD-ROM disk contains a Setup program to install the 
Upgrade software. Setup copies the Upgrade utilities into an UPGRADE directory 
that it creates on a user-specified drive. 

To run the Upgrade utilities, you must log on with administrative privileges on the servers 
running LAN Manager and Windows NT Server. 

To install the Upgrade Utilities on a server running LAN Manager
   1.  On the Windows NT Server 3.51 CD-ROM disk, change to the directory 
   \UPGRADE.LM2. 
   2.  Change to the directory that corresponds to the platform that you are upgrading to: 
\X86, \ALPHA, or \MIPS.

If you are upgrading to an x86 computer without a CD-ROM drive, insert the floppy 
disk labeled "Upgrade Utilities Disk for LAN Manager for x86 Systems," and change to that 
drive.

3.  Type 
        setup <drive:> 
where drive is the destination for the upgrade files. Note that this can be an existing 
network connection. Setup copies files to the UPGRADE directory that Setup creates on 
the specified drive.

================
3.0  Upgrade Notes, Corrections, and Clarifications

-----------------------
3.1  Upgrade Guide Available Online

The Upgrade Guide manual is available in online format on the Windows NT 3.51 CD-ROM 
disk.

-----------------------
3.2  Services for Macintosh

If a LAN Manager Macintosh volume uses a directory name with an unsupported extended 
character, Sfmconv skips the volume during conversion and generates an entry in 
SFMCONV.LOG similar to the following:

   error: open error on G:\AIOSHARE\~AFP\VOLINFO.AFP,
   error=3 The system cannot find the path specified.

where the directory name AIOSHARE contains unsupported characters.

If this error occurs, check unconverted volumes for directory names with any of the 
unsupported characters listed in item 5.3. To convert the volumes, remove these characters 
prior to running Sfmconv.

SFMCONV.EXE should be run only once on each drive. If you do not obtain the desired 
results, start the SFM (Services for Macintosh(R)) process over from the beginning: delete 
all SFM-related files on the Windows NT Server computer and run the Services for 
Macintosh conversion again from the Windows NT Upgrade Manager.

The following paragraph clarifies the Sfmconv section on page 160 of the Upgrade Guide. 
The first paragraph under "Comments" should read:

"To convert Services for Macintosh, you must preserve Macintosh volume structure 
exactly as it is under LAN Manager.  The volume **that you are converting to** must 
have the same structure, **including drive letters and subdirectories** as the source 
LAN Manager for Macintosh volume. All partitions must be NTFS and Services for 
Macintosh must be installed. Sfmconv operates only on NTFS volumes." 

If the volume structure on the destination does not match the source, prior to running 
WNTUPMGR.EXE,  rename drive letters using the Windows NT Disk Administrator.

-----------------------
3.3.  Command Line Options

Page 264 of the Upgrade Guide incorrectly states that the /codepage:### option is 
applicable to USERCONV.EXE. USERCONV takes no command line options.

-----------------------
3.4  USERCONV Exit Option

USERCONV also can be exited by pressing the ESC key.  However, if you do this, you will 
lose any changes that you have made to USERCONV parameters.

-----------------------
3.5  RESTENV Can't Reestablish a Network Share

Several users have reported that after upgrading, they are no longer connected to some 
previous network connections.  In most cases, this is caused by the fact that the network 
connection was established with a different password.  Since the Upgrade Manager is 
unable to store this password, it cannot reestablish the connection.
If you have important persistent connections, verify that these connections are established 
by comparing the new configuration with the connections listed under "Uses" in 
ADVISORY.TXT.

-----------------------
3.6 Net Logon Service Parameters

Because of the differences between LAN Manager and Windows NT Server 3.51, Net 
Logon service parameters should not be transferred from the LAN Manager server to the 
new Windows NT Server computer. This is now reflected in Windows NT Server Upgrade 
Manager Express upgrade. When RESTENV.EXE is run, it will use the /nonetlogon option.
If you do need to transfer Net Logon service settings, you can remove the /nonetlogon 
option from the RESTENV command line while running Windows NT Server Upgrade 
Manager Custom upgrade.

-----------------------
3.7 ACLCOMP.EXE

Windows NT Server Upgrade Manager Express upgrade no longer runs the ACLCOMP 
utility. ACLCOMP is a supplemental utility that compares data converted by ACLCONV 
with a file created by ACLLIST, serving as an additional quality-assurance check to the 
upgrade process. On large directories with many ACLs, ACLCOMP can take an extended 
amount of time (sometimes up to 72 hours) to complete.  If you choose to run this utility, 
you can run it from the command line after the conversion is completed.

-----------------------
3.8 PORTUAS: Preventing Interruptions from a BDC Synchronization

If PORTUAS is transferring more than 500 LAN Manager users and there are existing backup 
domain controllers (BDCs) in the domain, there is a possibility of the BDC starting a full 
replication because of the amount of changes made to the log during the PORTUAS process. 
To prevent this from happening, add the ChangeLogSize parameter to the Primary Domain 
Controller Registry and set the value to 4000000 (HEX).  Since this parameter setting does 
not degrade system performance, it is advisable to leave it at the 4000000  (4MB) setting, 
rather than returning it to the 64K default setting.  This will ensure that the domain's 
database will not be completely replicated if large changes are made in the future. This 
parameter should be the same on all BDCs to ensure that when a BDC is promoted to a PDC, 
it will have that same ChangeLogSize value.

Use REGEDT32.EXE to make the following changes to the Registry on the Windows NT 
Server PDC that PORTUAS will be run on.  The range for ChangeLogSize is between 64K 
and 4MB, decimal.   The PDC must be rebooted in order for the change to take effect.

Add the following value to the registry:

HKEY_LOCAL_MACHINE

Key Name:	SYSTEM\CurrentControlSet\Services\NetLogon\Parameters
Name:		ChangeLogSize
Type:		REG_DWORD
Data (New):	4000000 (HEX)


